DO NOT MERGE: chore: Switch from jest to node test runner #58
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a showcase for trying out node's test runner. See findings below.
before() setup failures
before()failures are not very elegantly handled:Node should rather explicitly call out that the
before()function has failed instead of listing potentially hundreds of tests that failed because of it. The results are roughly identical, whether you use an assertion to failbefore()or throw an error.TypeScript
Since Node can't interpret TypeScript, you have to use a loader like
ts-nodeorswc:node --loader ts-node/esm --test-reporter spec --test tests/unit/reporter.spec.tsNot an obstacle.